Greptile Summary

This PR adds a new Tier 2 warn-version-readme-changelog-sync hook rule that fires whenever a version manifest (package.json, plugin.json, or marketplace.json) is written with a semver "version" field, nudging the agent to keep README.md and CHANGELOG.md in sync. It also bumps all four version surfaces to 1.15.0 and ships the reconstructed CHANGELOG.md established in the stacked PR #21.

• New rule (hooks/rules/rules.yaml + rules.json): pattern-matches manifest file paths and \"version\": \"X.Y.Z\" content; emits a non-blocking warn with a workflow suggestion; 11 tests added.
• Version bump: package.json, .claude-plugin/plugin.json, and .claude-plugin/marketplace.json all aligned to 1.15.0; README.md header line updated to match.
• CHANGELOG.md: new file with reconstructed history from 1.1.0 through 1.15.0, including the 1.15.0 entry documenting the dogfooding observation.

Path to 5/5 Confidence

1. Fix the bypass instruction for JSON manifest files — hooks/rules/rules.yaml and hooks/rules/rules.json, message: block of warn-version-readme-changelog-sync. Remove the sentence suggesting # hook-bypass: as an inline comment inside a JSON file. JSON has no comment syntax; following that instruction literally corrupts the manifest. Replace with guidance that is JSON-safe (e.g., describe only the tool-call-level bypass mechanism, or a separate-commit strategy).

2. Unify the bypass comment syntax — the message: field uses # (shell-style) but the allows-bypass-marker test case uses // (JS-style). Pick one and make both consistent. The framework schema example uses //.

3. Add the missing [1.15.0] reference link and fix [Unreleased] — CHANGELOG.md line 228. Insert [1.15.0]: https://github.com/DojoCodingLabs/make-no-mistakes-toolkit/releases/tag/v1.15.0 between [Unreleased] and [1.14.0], and update the [Unreleased] compare base from v1.14.0 to v1.15.0. A suggestion block is already attached inline.

Confidence Score: 3/5

The manifest bumps and README/CHANGELOG changes are safe; the bypass instructions in the new rule's warning message would corrupt a JSON manifest if followed literally.

The new rule's warning text directs users to embed a # hook-bypass: comment inside package.json (or the other JSON manifests), but JSON has no comment syntax. Following that instruction as written would write invalid JSON, breaking npm install and every tool that reads the manifest. The test case allows-bypass-marker reinforces the broken approach and also uses // while the prose says #. The CHANGELOG footer is additionally missing the [1.15.0] reference link and has a stale [Unreleased] compare URL pointing at v1.14.0.

hooks/rules/rules.yaml and the generated hooks/rules/rules.json — the bypass guidance in the message field needs to drop the JSON-comment approach and only describe the tool-call-level bypass or a JSON-safe alternative.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Claude writes/edits manifest file] --> B{file_path matches\npackage.json /\nplugin.json /\nmarketplace.json?}
    B -- No --> Z[Pass — no action]
    B -- Yes --> C{content contains\n'version': 'X.Y.Z'?}
    C -- No --> Z
    C -- Yes --> D{bypass marker\npresent in any\ntool_input field?}
    D -- Yes --> Z
    D -- No --> E[WARN: version-readme-changelog-sync\nexit 0 message to stderr]
    E --> F[Agent nudged to update\nREADME.md Version line\n+ CHANGELOG.md entry]

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
hooks/rules/rules.yaml:2222-2236
**Bypass instruction produces invalid JSON**

The warning message tells users to add `"# hook-bypass: version-readme-changelog-sync"` as a comment near the version field in `package.json`, `plugin.json`, or `marketplace.json`. JSON has no comment syntax — embedding either `#` or `//` style comments produces a file that fails JSON parsing, which would break `npm install`, CI pipelines, and any tool reading the manifest. The test case `allows-bypass-marker` reinforces the same invalid pattern (using `//` while the message text says `#` — a second inconsistency). The bypass message should drop the embedded-comment suggestion entirely for JSON targets and only describe the tool-call–level mechanism ("pass it on the Write call"), or document a safe alternative.

### Issue 2 of 2
CHANGELOG.md:228-229
The `[1.15.0]` reference link is missing from the footer, so the `## [1.15.0]` heading in rendered Markdown is not a clickable link. The `[Unreleased]` compare URL also still points to `v1.14.0` instead of the just-released `v1.15.0`.

```suggestion
[Unreleased]: https://github.com/DojoCodingLabs/make-no-mistakes-toolkit/compare/v1.15.0...HEAD
[1.15.0]: https://github.com/DojoCodingLabs/make-no-mistakes-toolkit/releases/tag/v1.15.0
[1.14.0]: https://github.com/DojoCodingLabs/make-no-mistakes-toolkit/releases/tag/v1.14.0
```

_{Reviews (1): Last reviewed commit: "docs(changelog): add 1.15.0 entry (dogfo..." | Re-trigger Greptile}